The Building Blocks of Performance

Over the course of my career, I have come to think about performance as the product of a stack of conditions.

At the top sit the outcomes everyone wants. The results. The impact. The performance we can point to and defend.

Beneath outcomes sits the system. The way work actually moves. How decisions get made. How information travels. How incentives align or fail to. Who has authority. Who has accountability. Where friction lives. What gets rewarded. What gets quietly punished.

Beneath the system sits the team. Not as a sentimental nod to people being our greatest asset, but as a practical reality. Who is in the room changes what the room can see. Every hire changes the system. Every team creates a different range of possibility. The team determines how conflict is handled, whether trust exists, what gets surfaced early and what everyone silently agrees not to name.

And beneath the team sits the leader. Not the title. Not the role. The person. Who are you when pressure rises? What do you value when the easy answer and the right answer are not the same? How predictable are you to the people around you? What conditions do you create without realizing you are creating them?

Self. Team. System. Outcomes. Four layers. Each one shaping what is possible in the layer above it.

Once I had language for this, many things I had seen over the years started making more sense.

The executive who could not understand why a high-profile hire was failing, even though the resume was impeccable and the references glowed. The problem, as it turned out, was not just the person. It was the mismatch between the adaptive demands of the role and the way success had been assessed. We hired for pedigree and got predictability. The environment required learning speed, trust-building and judgment under pressure. The conditions were wrong before the person even arrived.

The team that said it valued candor, innovation and collaboration while operating in a system that rewarded caution, political fluency and silence at the wrong moments. The issue was not hypocrisy. It was design. Their rituals, incentives and reporting relationships taught one thing while their values statement claimed another.

The physician sitting at her kitchen table at nine o’clock at night finishing work she should never have had to carry into the evening in the first place. Not because she lacked resilience. Not because she had suddenly become less committed to patients. Because the system had been designed in ways that consumed her time, thinned her energy and converted a calling into a sequence of frictions. That is not burnout as a character flaw. That is design showing up in human form.

That is why I do not think of leadership primarily as a matter of style. Nor as the product of innate qualities like resilience or grit.

I think of it as the design of conditions.

•   •   •

Leadership literature often loses me. Too much of it is built around attributes, behaviors or philosophies detached from the machinery of how organizations actually work. Be more authentic. Be more visionary. Be more decisive. Communicate more clearly. Build a better culture.

But what does any of that mean if the system punishes the very behavior you say you want? What does authenticity matter if the leader has never done the work to know who they are? What does vision matter if the team itself has been constructed in a way that narrows what’s possible? What does culture mean absent the structures and incentives that reinforce it? What does delivering outcomes mean if people are required to act heroically to achieve them?

This is a hard problem because every layer in the stack can mask what is broken beneath it. A strong team can compensate for a weak system for a while. A strong leader can hold together a brittle team longer than seems rational. A lucky quarter can disguise flawed systems. And when those compensations are in place, organizations tell themselves flattering stories. We are scrappy. We are resilient. We know how to get things done around here.

Maybe. Or maybe you are watching talented people absorb dysfunction personally because the system has not earned the right to ask less of them. That is the risk of starting at the top of the stack. You see the symptom and mistake it for the cause.

Poor outcomes? Push performance harder. A broken operation? Reorganize. A struggling team? Replace people. Anxious culture? Slap values on the wall and call it transformation.

But when leaders intervene at the wrong layer, they create churn rather than change. New faces. Same frustrations. New rhetoric. Same incentives. New strategy. Same behavior. Different movie poster. Same plot.

•   •   •

The Performance Stack is about working in the opposite direction.

We are not going to begin with outcomes and work backward through the usual managerial logic. We start where durable performance actually begins. With the self. Leaders who do not know who they are create instability, whether they mean to or not. Their teams learn to read mood rather than principle. They navigate personality rather than trust consistency. And no system built on those terms stays healthy for long.

From there, we move to the team. Your people are not a supporting function to the strategy. They are the strategy. Every hiring decision is a design decision. Every ritual is a structural signal. Every question of alignment, trust, development and culture lives here first before it appears in a dashboard later.

Then we move to the system. At scale, design sets the ceiling. Leaders can compensate for structural limits for only so long. After that, the system wins. It always does.

And only then do we arrive where most organizations prefer to start. Outcomes. Not as mystery. Not as luck. Not as the residue of charisma or heroic effort. But as the predictable, if often delayed, consequence of the conditions beneath them.